Why

MA0042 already avoids suggesting await using for direct new on Stream, DbConnection, and DbCommand subclasses when DisposeAsync is not overridden. The same false-positive pattern exists for other common framework base types whose default DisposeAsync remains synchronous.

What changed

• Extended MA0042 await-using analysis to handle direct new for:
  • DbDataReader
  • DbTransaction
  • DbBatch
  • TextWriter
• Reused the existing subclass override check so diagnostics are still reported when the concrete type (or an intermediate base) overrides DisposeAsync.
• Kept existing behavior for factory-returned instances (Create*() methods): diagnostics remain, because the runtime type may still provide an async override.

Tests

Added focused coverage in DoNotUseBlockingCallInAsyncContextAnalyzer_AsyncContextTests for each added base type:

• direct new without DisposeAsync override -> no diagnostic
• factory-returned instance -> diagnostic
• direct new with override -> diagnostic
• direct new with override in intermediate base -> diagnostic

Documentation

Updated docs/Rules/MA0042.md known limitations to document the added base types and examples for direct-instantiation vs factory behavior.

Contributes to #1134